Hell Everyone, I am using DOORS V9.6 I am trying to create a Requirement Traceability Matrix (RTM) that looks like ( Please look at File Table 10 that is attached). I have my modules linked up, and in the CAR-PS module- under RTM CAR-PS View you can see the all the information necessary to make the RTM.
I edited the DXL script under SRS Req ID, QM and TT columns in order to display the customer attributes- but as you can see each column simply lists ( dumps all the data and does not keep the correct formatting) I need it to be formatted ( For example HW-SRS-2 has a QM of Test and a TT: Start and Cruise) In other words to make it look like Table 10 Perhaps the SRS Req ID, QM and TT columns need to be combined into 1 but I was not able to do this successfully and keep the correct format
I am attaching the DOORS file Thank you
Alex_4IBM - Wed Jan 20 10:54:37 EST 2016 |
Re: Creating a Requirement Traceability Matrix in DOORS I think the problem might be in using multi-valued enumerated attributes for "QM" and "TT". When you display enumerated types like that and they have multiple values selected, they will display each value on a separate line. One workaround might be to create enumerated types for "QM-Test" and "QM-Display". Create enumerated types for "TT_Start", "TT_Stop", and "TT_Cruise". The default values for these would be blank. This might be one way to attack the display problem, if it's essential to have the results aligned like your example. Here's an example of the resulting view, if you use that approach. I also attached the updated project.
Attachments Files_to_Upload2.dpa |
Re: Creating a Requirement Traceability Matrix in DOORS Chris Annal - Thu May 05 11:31:11 EDT 2016 I think the problem might be in using multi-valued enumerated attributes for "QM" and "TT". When you display enumerated types like that and they have multiple values selected, they will display each value on a separate line. One workaround might be to create enumerated types for "QM-Test" and "QM-Display". Create enumerated types for "TT_Start", "TT_Stop", and "TT_Cruise". The default values for these would be blank. This might be one way to attack the display problem, if it's essential to have the results aligned like your example. Here's an example of the resulting view, if you use that approach. I also attached the updated project.
Thanks Chris, this is an interesting approach, but won't satisfy what I need to do because the actual Module I am working on has more options as QM and TT and having separate attributes is not very user friendly.
When pulling this attribute from another module based on linking- I was able to create this variable in the same line by printing everything in one line ( DXL script) and then enters spaces between entries |
Re: Creating a Requirement Traceability Matrix in DOORS What you ask for is quite easy to do by writing a custom dxl script -- doing what you ask in view is a little harder and doesn't add any value to the final excel export. |
Re: Creating a Requirement Traceability Matrix in DOORS DOORSHAM - Thu May 05 13:49:17 EDT 2016 What you ask for is quite easy to do by writing a custom dxl script -- doing what you ask in view is a little harder and doesn't add any value to the final excel export. Can you elaborate on this? What I am currently doing is the following. 1) In a different Module, I use the link wizard to view incoming links, this is how I bring in the QM and TT attributes in separate columns 2) Now I can right click and edit the DXL script that the Link wizard uses, and split up the view
Is there a way to do this from the main module which contains the QM and TT?
Or an RPE script of some type that can keep the table creation increment by requirement not QM or TT |
Re: Creating a Requirement Traceability Matrix in DOORS Alex_4_IBM - Thu May 05 13:54:01 EDT 2016 Can you elaborate on this? What I am currently doing is the following. 1) In a different Module, I use the link wizard to view incoming links, this is how I bring in the QM and TT attributes in separate columns 2) Now I can right click and edit the DXL script that the Link wizard uses, and split up the view
Is there a way to do this from the main module which contains the QM and TT?
Or an RPE script of some type that can keep the table creation increment by requirement not QM or TT If you want to do it the easy way just create a dxl script that creates a comma delimited file that has a format similar to:
SYS Req ID,System Requirment,SYS Req ID,QM,TT
Script would run in the CAR-PS module and would pull in the data from the linked modules. |
Re: Creating a Requirement Traceability Matrix in DOORS Alex_4_IBM - Thu May 05 11:47:12 EDT 2016 Thanks Chris, this is an interesting approach, but won't satisfy what I need to do because the actual Module I am working on has more options as QM and TT and having separate attributes is not very user friendly.
When pulling this attribute from another module based on linking- I was able to create this variable in the same line by printing everything in one line ( DXL script) and then enters spaces between entries Yes, that works probably better. I was looking at the attributes you were using and seeing that they only had a couple enumerated values, my approach was an acceptable one - but if you want to display multiple-selected values you could use the approach in https://www.ibm.com/developerworks/community/forums/html/topic?id=cf3a396d-7326-4a86-bfea-6b92bea6c0dd&ps=25 Good Luck! |